Multi-perspective business process configuration

ABSTRACT

A computer-implemented method for configuring a business process includes configuring a solution map and deriving a pre-configured set of collaborative business scenarios based on the solution map. The pre-configured set of collaborative business scenarios is then configured and a pre-configured set of event driven process chains is derived based on the configured set of collaborative business scenarios. Finally, the pre-configured set of event driven process chains is configured.

DESCRIPTION OF THE RELATED ART

Implementation of enterprise resource planning (“ERP”) software is amajor undertaking for a business organization. Typically, thisimplementation affects all aspects of the organization. As a result,failure to correctly and timely execute the implementation can havefar-reaching consequences.

There are various reasons and pitfalls that can potentially impede asuccessful ERP software installation. One reason could be that theimplementation partners do not have a correct grasp of theorganization's business requirements, either through their own fault orperhaps an organization not effectively communicating to the installersdue to varying levels of abstraction of end users. This can result in anincorrect implementation and would thus require an expensive fix toresolve the issues. Alternatively, ERP software itself could be theculprit in preventing a successful installation. If the ERP software isnot flexible enough to be applied to the organizational requirements,delays will more than likely occur.

Configuration of the internal processes of enterprise systems is made ondifferent hierarchical levels within an organization. For example, thesenior management will influence the configuration process on a moreabstract level whereas technical analysts need a very detaileddescription of the process in order to perform configuration. Hence,their requirements towards the presentation need to be different(abstract, easy to understand models for the senior management, detailedtechnical descriptions for technical analysts, detailed businessprocesses for business analysis). The problem from using differentlanguages to support the different types of decision makers within anenterprise configuration process is then to integrate these models inorder to establish a communication basis between the types of decisionmakers. An absence of such a communication basis will ultimately lead tothe loss of configuration at the different managerial levels.

In view of the foregoing, it may be useful to provide methods andsystems that facilitate a flexible installation of ERP software thatallows for varying levels of abstraction.

SUMMARY OF EMBODIMENTS OF THE INVENTION

The present invention is described and illustrated in conjunction withsystems, tools and methods of varying scope which are meant to beexemplary and illustrative, not limiting in scope.

A computer-implemented method for configuring a business process, inaccordance with an exemplary embodiment, includes configuring a solutionmap and deriving a pre-configured set of collaborative businessscenarios based on the solution map. The pre-configured set ofcollaborative business scenarios is then configured and a pre-configuredset of event driven process chains is derived based on the configuredset of collaborative business scenarios. Finally, the pre-configured setof event driven process chains is configured.

A computer-implemented method for configuring a business process, inaccordance with another exemplary embodiment, includes configuring asolution map based on a business blueprint and deriving a pre-configuredset of collaborative business scenarios based on the solution map.Deriving the pre-configured set of collaborative business scenariosincludes identifying one or more impacted collaborative businessscenarios, making changes to the one or more impacted collaborativebusiness scenarios based on the configured solution map; andre-establishing consistency in a collaborative business scenariomodel-base. The pre-configured set of collaborative business scenariosis configured and this configuration involves performing a high-levelbusiness process analysis and configuring the pre-configured set ofcollaborative business scenarios based on the high-level businessprocess analysis. A pre-configured set of event driven process chains isderived based on the configured set of collaborative business scenarioswherein deriving the pre-configured set of event driven process chainsincludes identifying one or more impacted event driven process chains,making changes to the one or more impacted event driven process chainsbased on the configured set of collaborative business scenarios andre-establishing syntactical consistency in an event driven process chainmodel-base. Finally, the pre-configured set of event driven processchains is configured by performing detailed-level analysis andconfiguring the pre-configured set of event driven process chains basedon the detailed-level business process analysis.

In addition to the aspects and embodiments of the present inventiondescribed in this summary, further aspects and embodiments of theinvention will become apparent by reference to the drawings and byreading the detailed description that follows.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a typical network of anorganization;

FIG. 2 is a block diagram illustrating integrated process models, inaccordance with an exemplary embodiment;

FIG. 3 is a flowchart illustrating a process for configuring a businessprocess, in accordance with an exemplary embodiment;

FIG. 4 is a flowchart further illustrating the process 302 forconfiguring a solution map of FIG. 3; in accordance with an exemplaryembodiment;

FIG. 5 illustrates an exemplary solution map, in accordance with anexemplary embodiment;

FIG. 6 is a flowchart further illustrating the process 304 for derivinga pre-configured set of collaborative business scenarios of FIG. 3, inaccordance with an exemplary embodiment;

FIG. 7 illustrates a linked database that defines softwarefunctionality, in accordance with an exemplary embodiment;

FIG. 8 is a flowchart further illustrating the process 606 forre-establishing consistency in the collaborative business scenario-baseof FIG. 6, in accordance with an exemplary embodiment;

FIG. 9 is a flowchart further illustrating the process 306 forconfiguring the pre-configured set of collaborative business scenariosof FIG. 3, in accordance with an exemplary embodiment;

FIG. 10 is an exemplary block diagram illustrating how collaborativebusiness scenarios are configured, in accordance with an exemplaryembodiment;

FIG. 11 is a flowchart further illustrating a process 308 for derivingthe pre-configured set of event driven process chains of FIG. 3, inaccordance with an exemplary embodiment;

FIG. 12 illustrates a linked database that portrays how event drivenprocess chains are changed in view of collaborative business scenarios;in accordance with an exemplary embodiment;

FIG. 13 is a flowchart further illustrating the process 1106 forre-establishing consistency in the event driven process chain model-baseof FIG. 11, in accordance with an exemplary embodiment;

FIG. 14 is a flowchart further illustrating the process 310 forconfiguring the pre-configured set of event driven process chains, inaccordance with an exemplary embodiment;

FIG. 15A is an exemplary block diagram illustrating a pre-configuredevent driven process chain, in accordance with an exemplary embodiment;

FIG. 15B is an exemplary block diagram illustrating a configuredpre-configured event driven process chain, in accordance with anexemplary embodiment;

FIG. 16 is an exemplary block diagram illustrating a completedmeta-model, in accordance with an exemplary embodiment; and

FIG. 17 is a block diagram illustrating various perspectives involved inimplementing enterprise resource project software.

DETAILED DESCRIPTION

An aspect of the present invention contemplates a variety of methods,systems and data structures for configuring a business process. Byutilizing a solution map that fully describes how a business functionsin conjunction with a pre-configured set of collaborative businessscenarios (“CBS”)/models, an organization can efficiently and correctlybe outfitted with ERP software. As a result, the typical inefficienciesand pitfalls associated with prior art ERP software implementation isavoided.

FIG. 1 is a block diagram illustrating a typical network of anorganization 100. Included in architecture 100 are multiple servers 102,multiple clients 104, a firewall 106, all of which are bi-directionallycoupled via a local area network 108. Also included is a network 108that allows for communication with a number of vendors V₁ through V_(N)and customers CU₁ through CU_(N). Additionally, communication can beinitiated with local area network 108 from remote site 110, via network108 and firewall 106. Architecture 100 forms the basis for anorganization to perform its required tasks such as procurement andshipping.

FIG. 2 is a block diagram 200 illustrating integrated process models, inaccordance with an exemplary embodiment. Integrated process models allowfor varying degrees of abstraction. For example, region 202 illustratesa high-level solution map of an organizational framework. Thisparticular region only shows the core process models 204. Region 206expounds on models 204 by showing them in greater detail ascollaborative business scenarios (CBS). Finally, the greatest level ofdetail is displayed in region 208. Region 208 shows how the model 204interacts as a detailed process model. Typically, region 208 is thepreferred view of a business analyst while region 202 is the viewpreferred by management.

It should be noted that various terms and phrases are used to describeexemplary aspects. However, these terms are merely descriptive and otherequivalent terms and phrases can be substituted without departing fromthe spirit and scope of the present invention. For example, “solutionmap” could alternately phrased as “models for the managementperspective”, “collaborative business scenarios” could perhaps ereferred to as “models for the technical analyst perspective” and“event-driven process chain” could also be referred to as “models forthe business analyst perspective”.

FIG. 3 is a flowchart illustrating a process 300 for configuring abusiness process, in accordance with an exemplary embodiment. After astart operation, a solution map is configured and a pre-configured setof CBS's is derived based on the solution map, at operations 302 and304. The pre-configured set of CBS's is then configured and apre-configured set of EPC's is derived, based on the configured set ofCBS's, at operations 306 and 308. Finally, at operation 310, thepre-configured set of EPC's is configured and process 300 is thencomplete. Each of the various operations of process 300 will beexplained in greater detail subsequently.

FIG. 4 is a flowchart further illustrating the process 302 forconfiguring a solution map of FIG. 3; in accordance with an exemplaryembodiment. After a start operation, a business blueprint is obtained atoperation 402. The business blueprint details all of the variousprocesses of a business organization. Using the blueprint, a solutionmap, used to implement ERP software, is then configured at an operation404. FIG. 5 illustrates an exemplary solution map 500, in accordancewith an exemplary embodiment. Solution map 500 includes a list ofvarious operations 510 along with the various tasks 520 associated witheach individual operation 510. A detail 530 of the tasks 520 can furtherbe displayed by clicking on the individual task 520.

FIG. 6 is a flowchart further illustrating the process 304 for derivinga pre-configured set of collaborative business scenarios of FIG. 3, inaccordance with an exemplary embodiment. First, impacted collaborativebusiness scenarios are identified, at an operation 602, and changes aremade to the affected CBS's as defined by the solution map, at operation604. After the changes are affected, consistency is re-established inthe model. The “pre-configured” set of collaborative business scenariosis in a state as to define a generic organization. By configuring thepre-configured set of CBS's, the CBS's are customized to match thetargeted business organization.

FIG. 7 illustrates a linked database 700 that defines softwarefunctionality, in accordance with an exemplary embodiment. Linkeddatabase 700 is divided into two portions: a solution map portion 710and a CBS portion 720. Tables 730 define various operations andassociated tasks and links 740 define how these various operations areorganized in relation to each other.

FIG. 8 is a flowchart further illustrating the process 606 forre-establishing consistency in the collaborative business scenario-baseof FIG. 6, in accordance with an exemplary embodiment. After a startoperation, semantic consistency is re-established via an operation 608.Semantic consistency refers to the necessary removal of functionsresulting from the deletion of a related function. After operation 608,syntactic consistency is re-established and is verified in terms of thesemantics, at operations 610 and 612. Syntactic consistency is thenecessity to conform to the rules of modeling technique. To furtherillustrate, a software operation 614 is deleted. As a result, operations618 and 620 also need to be deleted. Operation 622 was created toreplace operations 618, 614 and 620.

FIG. 9 is a flowchart further illustrating the process 306 forconfiguring the pre-configured set of collaborative business scenariosof FIG. 3, in accordance with an exemplary embodiment. A high-levelbusiness process analysis is undertaken, at an operation 902, and thenpre-configured CBS's are configured based on the analysis, at anoperation 904. FIG. 10 is an exemplary block diagram 1000 illustratinghow collaborative business scenarios are configured, in accordance withan exemplary embodiment. In diagram 1000, a demand planning operation1002 is defined on a vendor side of operations. Related operations 1004,1006, 1008 and 1010 are also defined. At a point in between operations1006 and 1008, control of the process is turned over to a buyer.Operation 1002 can be further defined in box 1012.

FIG. 11 is a flowchart further illustrating a process 308 for derivingthe pre-configured set of event driven process chains of FIG. 3, inaccordance with an exemplary embodiment. First, impacted EPC's areidentified at operation 1102. Then, changes are made to the identifiedEPC's, based on CBS's, at an operation 1104. Finally, at an operation1106, consistency is re-established in the EPC model-base. FIG. 12illustrates a linked database 1200 that portrays how event drivenprocess chains are changed in view of collaborative business scenarios;in accordance with an exemplary embodiment. Database 1200 is dividedinto two parts: a CBS part 1202 and an EPC part 1204. CBS tables areindicated at 1206, 1208 and 1210 while EPC tables are located at 1212,1214 and 116. EPC's are changed in view of CBS's via tables 1218, 1220and 1222.

FIG. 13 is a flowchart further illustrating the process 1106 forre-establishing consistency in the event driven process chain model-baseof FIG. 11, in accordance with an exemplary embodiment. At an operation1302, semantic consistency is re-established and then syntacticconsistency is re-established, at an operation 1304. Syntacticconsistency is then verified in terms of the semantics, at operation1306.

FIG. 14 is a flowchart further illustrating the process 310 forconfiguring the pre-configured set of event driven process chains, inaccordance with an exemplary embodiment. First, a detailed-levelbusiness analysis is undertaken at an operation 1402. Then, event drivenprocess chains are configured, at an operation 1404, based on theanalysis.

FIG. 15A is an exemplary block diagram illustrating a pre-configuredevent driven process chain 1500A, in accordance with an exemplaryembodiment. EPC's “out of the box”, are pre-configured in that they areset up to resemble a generic business process and are then customized orfurther configured to fit the activities of the target organization.Pre-configured process chain 1500A describes a generic process ofinvoicing and payment.

FIG. 15B is an exemplary block diagram illustrating a configuredpre-configured event driven process chain 1500B, in accordance with anexemplary embodiment. Process 1500B only includes a subset of theprocess chain 1500A because this particular organization'sinvoicing/payment process is not that complicated. It should be notedthat process chain 1500A is merely a starting point and that it verywell become more complicated as opposed to less comprehensive whenapplied to define an organization's processes. For clarity, it shouldalso be noted that symbol 1502 represents an “AND” function and thatsymbol 1504 represents an inclusive “OR” function. Furthermore, “XOR”refers to an exclusive “OR” function.

FIG. 16 is an exemplary block diagram illustrating a completedmeta-model 1600, in accordance with an exemplary embodiment. Thecompleted meta-model is divided into various sub-models (as indicated bythe associated shading) such as the solution map model 1602,collaborative business scenario model 1604 and event driven processmodel 1606. Additionally included is SM-CBS integration relation 1608and CBS-EPC integration relation 1610.

FIG. 17 is a block diagram 1700 illustrating various perspectivesinvolved in implementing enterprise resource project software. Includedin block diagram 1700 are, as an example, three perspectives: managementperspective 1702, business analyst perspective 1704 and technicalanalyst perspective 1706. Management perspective 1702 is the mosthigh-level and does not include many details. Technical analystperspective 1706 contains all the required details for implementing ERPsoftware. In the middle, there is the business analyst perspective 1704which has a level of detail in between that of management 1702 andtechnical analyst. To help the various perspectives to implement the ERPsoftware, there are integration layers 1708 and 1710. Integration layer1708 is located between the management perspective 1702 and the businessanalyst perspective 1704 and helps to correctly map each perspective toeach other. Similarly, integration later 1710 is located in betweenbusiness analyst perspective 1704 and technical analyst perspective 1706and helps to map each perspective to each other.

While this invention has been described in terms of certain embodiments,it will be appreciated by those skilled in the art that certainmodifications, permutations and equivalents thereof are within theinventive scope of the present invention. It is therefore intended thatthe following appended claims include all such modifications,permutations and equivalents as fall within the true spirit and scope ofthe present invention.

1. A computer-implemented method for configuring a business processcomprising: configuring a solution map; deriving a pre-configured set ofcollaborative business scenarios based on the solution map; configuringthe pre-configured set of collaborative business scenarios; deriving apre-configured set of event driven process chains based on theconfigured set of collaborative business scenarios; and configuring thepre-configured set of event driven process chains.
 2. Thecomputer-implemented method as recited in claim 1 wherein the solutionmap is configured based on a business blueprint.
 3. Thecomputer-implemented method as recited in claim 1 wherein deriving thepreconfigured set of collaborative business scenarios comprises:identifying one or more impacted collaborative business scenarios;making changes to the one or more impacted collaborative businessscenarios based on the configured solution map; and re-establishingconsistency in a collaborative business scenario model-base.
 4. Thecomputer-implemented method as recited in claim 3 whereinre-establishing consistency in the collaborative business scenariomodel-base comprises: re-establishing a semantic consistency;re-establising a syntactic consistency; and verifying the syntacticconsistency in terms of the semantic consistency.
 5. Thecomputer-implemented method as recited in claim 1 wherein configuringthe pre-configured set of collaborative business scenarios comprises:performing a high-level business process analysis; and configuring thepre-configured set of collaborative business scenarios based on thehigh-level business process analysis.
 6. The computer-implemented methodas recited in claim 1 wherein deriving the pre-configured set of eventdriven process chains comprises: identifying one or more impacted eventdriven process chains; making changes to the one or more impacted eventdriven process chains based on the configured set of collaborativebusiness scenarios; and re-establishing syntactical consistency in anevent driven process chain model-base.
 7. The computer-implementedmethod as recited in claim 6 wherein re-establishing consistency in theevent-driven process chain model-base comprises: re-establishing asemantic consistency; re-establising a syntactic consistency; andverifying the syntactic consistency in terms of the semanticconsistency.
 8. The computer-implemented method as recited in claim 1wherein configuring the pre-configured set of event driven processchains comprises: performing a detailed-level business process analysis;and configuring the pre-configured set of event driven process chainsbased on the detailed-level business process analysis.
 9. Acomputer-implemented method for configuring a business processcomprising: configuring a solution map based on a business blueprint;deriving a pre-configured set of collaborative business scenarios basedon the solution map wherein deriving the pre-configured set ofcollaborative business scenarios includes: a) identifying one or moreimpacted collaborative business scenarios; b) making changes to the oneor more impacted collaborative business scenarios based on theconfigured solution map; and c) re-establishing consistency in acollaborative business scenario model-base; configuring thepre-configured set of collaborative business scenarios whereinconfiguring the pre-configured set of collaborative business scenariosincludes: a) performing a high-level business process analysis; and b)configuring the pre-configured set of collaborative business scenariosbased on the high-level business process analysis; deriving apre-configured set of event driven process chains based on theconfigured set of collaborative business scenarios wherein deriving thepre-configured set of event driven process chains includes: a)identifying one or more impacted event driven process chains; b) makingchanges to the one or more impacted event driven process chains based onthe configured set of collaborative business scenarios; and c)re-establishing syntactical consistency in an event driven process chainmodel-base; and configuring the pre-configured set of event drivenprocess chains wherein configuring the pre-configured set of eventdriven process chains includes: a) performing detailed-level analysis;and b) configuring the pre-configured set of event driven process chainsbased on the detailed-level business process analysis.
 10. Thecomputer-implemented method as recited in claim 9 whereinre-establishing the consistency in the collaborative business scenariomodel-base comprises: re-establishing a semantic consistency;re-establising a syntactic consistency; and verifying the syntacticconsistency in terms of the semantic consistency.
 11. Thecomputer-implemented method as recited in claim 9 whereinre-establishing consistency in the event-driven process chain model-basecomprises: re-establishing a semantic consistency; re-establising asyntactic consistency; and verifying the syntactic consistency in termsof the semantic consistency.